Prepare for docker builds in CI #842
Conversation
fdupress
force-pushed
the
docker-builds-in-ci
branch
from
fe424ef to
a6bb879
Compare
fdupress
force-pushed
the
docker-builds-in-ci
branch
2 times, most recently
from
14847f6 to
7d980bd
Compare
|
Right—putting this one on pause. It is silly to run this as a matrix when the base is build in all 3 jobs, but can't be shared. I need to rethink this—including whether we want to publish the base and build images. On the plus side, the build is working. |
fdupress
force-pushed
the
docker-builds-in-ci
branch
2 times, most recently
from
66611b8 to
b219d50
Compare
|
Notes to self on debugging the pipeline. All images got built. base-box got pushed successfully (and is in the container repository), but the push for build-box failed despite successful authentication. The failure happened shortly after 15 minutes. I may need to split the job, add dependencies between jobs, and make sure we cache as much of the work as possible. |
fdupress
force-pushed
the
docker-builds-in-ci
branch
3 times, most recently
from
2bdf33f to
a09a5b2
Compare
|
Note to self on debugging: https://ghcr.info/easycrypt/ needs to be accessed from a browser to give this repo permission to administer container images from CI. You learn something new every day. |
fdupress
force-pushed
the
docker-builds-in-ci
branch
from
a09a5b2 to
d3dfa31
Compare
|
Reviewers, I am interested in opinions on using Currently, it's Other than this decision: this is ready to go minus the REVERT ME. Container repository pollution will be cleaned up afterwards. This does not produce images with a full EasyCrypt or Formosa setup. (No |
This lays the groundwork for being able to generate dockerfiles in CI. I added a workflow_dispatch trigger so docker containers corresponding to specific branches (other than
latest, and release tags) can also be produced. Hopefully, I can use it to test the change.At the moment, the script tries to push the container to the GHCR—this hopefully should fail without first putting effort into setting credentials and a secure environment. (But who knows?)
latestmay be renamed tostableas part of (or before) this merge.